Or, in other words, the User Interface. There are several options and whether you choose to design your own application or source an existing application a decision should be made wisely. The implications are tremendous, and in particular when it comes to system maintenance and scalability. User interface considerations for an effective capture application: An application that is compiled and installed on a computer depending on the developers’ preference of operating system and development environment to create this application
It is a more controlled environment in which development, prototyping and refinement of the functionality of the ERM system, the revised business processes, the user interfaces and the training materials can be undertaken most effectively and with low risk to the business
E&A’s mobile content architecture services tailor core methodologies for taxonomy development, content tagging, and user interface design to the rapidly developing mobile marketplace
They tell be that the front end, or the user interface of the project was tested to emulate the anticipated load, but when they deployed it to production the system slowed down and then started crashing every few days
A while back, Software Advice, an online resource for wholesale distribution software , hosted a survey to see which consumer web user interface (UI) theme readers would like to see incorporated into business applications
Many organizations have been slow to build mobile applications, primarily because if they do have remote users, the current solutions (Citrix, Browser UI, etc.) have been good enough and there are concerns about diverting resources to developing and maintaining yet another user interface. But I think the mobile application for accessing content is a different opportunity altogether
Talk to an AP team and they will usually cite the four following problems: Inefficient use of resources: too much time, labor, and other resources Processing cycle takes too long and should be streamlined Not enough process control Not enough process visibility The appropriate ECM tools used effectively in conjunction with an ERP system can provide the following benefits: Reduced paper-handling and reduced labor Reduced misplaced or lost invoices Reduced storage costs Increased processing speed Decreased errors (higher accuracy) Fast, reliable, easy access to invoices, using the familiar ERP user interface On-time payments; more early payment discounts Auditable business processes with greater visibility, improving efficiency and facilitating regulatory compliance Some of these benefits, particularly benefits 1 – 6, can be derived almost immediately through invoice capture and digitization
Many organizations feel the only thing preventing ECM from becoming truly successful is a poor user interface that limited user uptake (for an excellent summary of this question, read the wisdom shared by experienced ECM practitioner Mike Alsup , who reminds us that user adoption is about far more than a slick user interface), it seems that everyone wants to believe that SharePoint 2010 is the answer to all of their prayers
Microsoft’s Internet Explorer turns 15 years old this year and for most ECM users, Explorer is the user interface back to their content repository
Provide faceting (filtering and sorting) mechanisms that help lead to query refinements; look at the directions Google has recently provided with their left panel (see example images below) Target a set of key business problems that search can help with and then work to make the data available and easily findable as part of your roll-out strategy User interfaces need to use paradigms people are already familiar with but which can be customized or extended for particular business needs where necessary